Repository navigation
ci: run the release and issue-assignment jobs in a release environment - #316
Merged
nickolas-dimitrakas merged 1 commit intoNov 17, 2026
Merged
Conversation
thomson-t
approved these changes
Nov 17, 2026
nickolas-dimitrakas
deleted the
ci/run-the-release-and-issue-assignment-jobs-in-a
branch
November 17, 2026 20:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Release automation should hold release credentials only where releases run. The release and issue-assignment jobs read the release bot token from repository-level secrets, which every workflow on every branch can read.
Programme
Standalone change, no programme.
What changes
releaseenvironment, which allows onlymain.No changelog entry, because nothing in the published package changes.
Linked work
Related: the same change in ROKT/rokt-sdk-react-native#336.
Rollout
Path: CI only; nothing is published.
releaseenvironment allows onlymain, with the token moving into it.Feature flags: none.
Turning it off: revert this pull request.
What we watch: the next release and issue assignment succeed.
Risks
Risk class: low.
Who
Written by: an automated coding agent (Claude Code), at an engineer's request.
Code reviewed before opening: an independent review agent; no person yet.
Checked: the changed workflows pass actionlint, and the environment's rule was read back through the GitHub API.
Not checked: a run on a real runner, which the next run after merging covers.
Size
Hand-written: 2 files, 4 lines added.
Generated: none.